V302 — Account-link identifier + real native CHR links (no fake CHR shortcuts)
===================================================================

A .lnk renamed to .CHR, or an empty "Drakhysyscharacters.CHR" placeholder, is
not a valid Baldur's Gate II character. Native BG2 expects actual CHR data.

On successful login as <accountname>, the router reads real CHR/BIO files in:
  Documents/Baldur's Gate II - Enhanced Edition/characters/<accountname>/
Only this account can be exposed through the native root characters/ view.

The router makes TEMPORARY NTFS HARDLINKS (not copies, backups, or fake files):
  characters/Drakhy.CHR -> characters/Drakhysys/Drakhy.CHR
  characters/Kronas.CHR -> characters/Kronas/Kronas.CHR
Only ONE account of the above may be visible in the shared root at a time, depending
on the selected login. The inactive account remains excluded from native BG2.

V302 ACCOUNT LINK RULE:
  Choose link = <accountname>
  If link != currently logged-in verified account -> DENY.
  If link == logged-in verified account -> READ / IMPORT / EXPORT only files
  belonging to characters/<accountname>.
  The router's active link identifier is stored with its native session state.
  Use SELECT_ACCOUNT_CHARACTER_LINK.bat while BG2 is logged in and open.
  When native BG2 displays a character, choose the real CHR filename, NOT a
  fictional accountnamecharacters.chr shortcut. Stock BG2 does NOT show folder
  link identifiers as selectable Import entries without a custom UI patch.

V302 FIX:
- An identical filename in another account folder no longer hides the active
  account's same-named file. A folder's verified registered identity determines
  which original file gets linked to BG2, not the CHR filename alone.
- Explicitly confirmed Drakhy/Kronas/Krokro ownership decisions still prevent
  a known misplaced file from being linked for the wrong account.
- The read-only CHECK_ACCOUNT_CHARACTER_ACCESS report warns when a .CHR file
  lacks a normal CHR header or is deliberately hidden as a known foreign file.
- An empty account folder can still export a new character; native Import shows actual CHRs only.
- LINK_LOGGED_ACCOUNT_CHR.bat opens the link selection tool and
  connects the selected logged-in account to the native Import/Export view. It requires an authenticated, active account and live router.

TEST:
  1. Exit all BG2/InfinityLoader windows. Unzip V302 and run
     SETUP_IN_GAME_ACCOUNTS.bat, choosing the correct game installation and
     Documents profile containing Baldur.lua. Do NOT reinstall over a running
     session. If your root characters/ contains loose CHR/BIO files, preserve
     wanted character files in their owner subfolders before setup: the
     inherited installer removes loose root files.
  2. Log in as ONE account in BG2. With that window still open, run
     SELECT_ACCOUNT_CHARACTER_LINK.bat from the extracted All Editors folder.
     Choose the link that equals the logged-in account; other names are denied.
  3. It must list the linked original CHR names. Refresh/reopen native Import.
  4. If empty, run CHECK_ACCOUNT_CHARACTER_ACCESS.bat and share
     ACCOUNT_CHARACTER_ACCESS_REPORT.txt. Confirm it names the SAME Documents
     profile as the running BG2 installation.
  5. Log out before switching to another account. Shared Windows Documents
     profiles cannot show two different native Import lists simultaneously:
     native BG2 scans one physical characters/ directory per profile.

No character files are copied between accounts, and no account registration
is recreated. Folder access is a router rule, not a Windows NTFS ACL. The
router cannot make an invalid/corrupted .CHR file importable.

Actual Windows BG2/InfinityLoader in-game results still require testing.
